I haven't really blogged much of anything before so I am learning how to explain this as well,
it is mostly my own problem in trying to explain it.

The IME is somewhat of a port but I am doing "from scratch" implimentations of the locale binding code so that there is as little friction between the IME and the System as possible.

once the initial library framework is in place with a couple of dummy functions I will be porting the Google Japanese IME along with trying to keep it "generic" and not just Japanese.

With regards polymorph, it is a re-write of a prior lost project so it will somewhat be "from scratch" but certainly integratable with UAE or another Emulator.

None of the techniques in either project are new (and I apologise in advance if I gave that impression), I am doing the Amiga specific code from scratch and trying to keep each part as small as possible.

for Polymorph itself the core routines will be processor ignorant and modules for x86 or MIPS or ARM processor Emulation can be written.

as for "Javascript" I am not sure, for Java or another "Virtual CPU" defined language will be easier to work with starting from the basic "operation codes"(the instruction numbers).

I've managed to get the planning parts done but as they are both projects I am doing for myself instead of helping someone else I am unsure what timeframe I would get them completed.

the current design for Polymorph would not lend itself to being easily portable to a new processor without re-writing the "Personality" modules for the new target.
the core library itself may be portable with few changes.

the first polymorph prototype was written for running Windows 3.x code on AmigaOS3.x being able to load and attempting to run the x86 code using an interpreter initially.
this was lost in a HDD failure some years ago (when I left Amiga Classics)

There are also a couple of options I want to explore with it which remain theory at this point however appear practical.

is only this filesystem affected?
is there anything other commands affected like this?

I would definitely ask more questions before writing a workaround
any workaround may introduce an unwanted bug...obviously?

@JosDuchIt - thank you for the constructive critique,

Yeah, I did do those entries in a rush and I was hoping
to answer questions about them but I was more surprised
about the lack of questions than anything else.

I've tried to sort out a more logical arrangement but I am
feeling I'm not so good with the blog and documentation
side of things.

I'm definitely not going to stop however,
as for previous work, some of it was experimental
other was NDA (and I still can't say more :(... )

As for what I can point to... there was a Picasso96 SDK for
AmigaE on the Classic Amiga's which I converted over.
(I wonder if that is still around?)

I have mostly done helper routines to fill gaps temporary
or otherwise in other peoples projects and I am actually
going forward with trying to produce a project of my own.

Perception is a Japanese InputMethodEditor to start with,
but also somewhat more generic in providing support
mechanisms to enable other languages that are difficult
to input using a normal keyboard with keymap as well.

I know there is little if any Japanese support currently,
and only specific VirtualMachine setups as well.

Polymorph is something of a hybrid between an Interpreter,
a JIT engine, and a recompiler.

I was asked if it used an intermediate "bytecode" like what
.NET does on Windows ... to this the answer is a definte
NO... it would not see "bytecode" from Java any different
from the CPU opcodes for an x86 or MIPS processor.

as there is the main library and then "Personality" modules
with the modules handling the specific details.

the standard CPU fetch-decode-execute loop is present,
in an abstraction, since the opcodes are translated direct
to the Host native processor.

I don't really know how to explain it otherwise without the
technical details, which as you have pointed out become
somewhat confusing.

well... I hope this answer helps even a little bit.
this thread also exists on AmigaWorld.net including some
negative comments from a couple of community members.

I'll just see what I can make and go from there, if they like
what they see or not, they have their opinion.

But like fishy_fis points out with regards any donations to me
the same rule as going to the shops applies..."Buyer beware"

I'll only ever ask anyone to think about donating based on what
they think of the project as it stands.

I'll be quite happy to hear "keep going" or "do your best",
or even a few constructively negative style comments.

I'm buying a machine anyway, it is just up to how quickly
I get started on actually coding instead of dealing with
the designs on paper.

@TheDaddy: a VM would only be one of several options,

But in all cases I still need to complete purchasing
the current sam440flex I am buying.

I have paid half of what is needed and still need to
pay the remainder.

Two people have shown support in donations as well.

the Total sum of donations and my own money has been a 50/50
split so far.

If anyone else wishes to help with a donation,
they too will be added to the pre-release list.

Additionally I will be asking for testing feedback
with regards what particular feature to focus on as well.

I know I need to re-write these to be more informative...

Can any suggestions be made from what I have blogged on
os4coding.net as well as the threads on AW+Amigans forums

Along with any questions about the projects themselves?

I'd like to clear up whats needed to complete each in a
timely manner and also what exactly they provide.

[EDIT]Mirrored from AmigaWorld.net
----
Perception IME - "Input Method Editor" framework allowing for Languages that are
not able to be entered into the computer by Keymap alone.

Chinese / Japanese / Korean and Arabic are 4 known examples.

you can enter the phrase "ohayougozaimasu" in using a qwerty style Keyboard,
and have it post-entry translated into 「おはようございます」
Using Japanese Hiragana as one example. (Japanese Language Hiragana Mode)
without losing the option to enter English or other European Languages.
----
Polymorph VM - "Virtual Machine" subsystem,

a support library for Emulators / JIT and Dynamic Recompiler systems along with
generic Virtual Machine functionality.

WHDLoad / ShapeShifter / Wine / PC-Task and Basilisk II are examples of this,
VirtualBox / VMware and QEMU are additional Examples as well.

The point of Polymorph is to actually provide a basic mechanism where
programs from any given "target" are made available on top of AOS4.x as
normal Applications.

From the AOS4.x it sees no difference between the "polymorphed" program and others,
from the "polymorphed" program it doesn't see "AOS4.x"... it sees the "target" system
instead.

Examples would be ...
running a Graphical "Java" application or "Windows" Application,
another example is encapsulating older "Classic" Amiga software and providing them
a more "complete" OS environment or a limited "Hardware only" Classic Amiga style
environment from which to run.

additionally...

Applications may be specifically written to make use of Polymorph in a hidden way,
and this would also provide the option of the "launcher" to make use of network options
where the "hidden" thread(s) may be running inside the "*virtual" container...
and the container can be pushed or pulled between machines.

the container wrapper (launch tool) may provide a basic presence locally and also
have the options to Disconnect and reconnect to the container later...

Allowing for "cluster" computing... similar to how distccd works in some parts.

There is also another experimental option with regards defining your own
container within polymorph... and that is "partial static" CPU definitions.

You can create your own CPU within some basic boundaries...
(number of registers, total memory, filesystem access)
and if the CPU definition is considered "volatile" then you can actively change
the functions provided by the "dynamic" section of the opcode table.

This would be most useful when dealing with encryption setups.
not only does the data get moved around but also the algorythm can be changed as well.

Think of this as a self-modifying Enigma machine needing extra keys,
not just the key for the message but also the modifications key as well.
[/EDIT]

I've also managed to work up to half-paid on my sam purchase
just organizing a last payment at the moment.

paypal problems making delays again! ugh :|

anyway... I have to run...literally.

If anyone wants to help with testing or donations...
Message me and I'll get back to you.

so far I have had a couple of donations that helped get past
the paypal quirks so far... prefer smaller donations
but anything donated will go to what it is donated for

Definitely an incentive to get Japanese support completely
functional by actually being here!!

**Bumping the Thread**
Status Updates : I'm in Japan for a month,
actively setting up for living here long-term.

Anyone who wants to can help towards my Amiga Developments,

My own documentation style does appear initially random,
And I have already decided that the *entirety* of the
Perception IME project will be fully published and documented
on os4coding.net for my own Blogging... along with at least
two source repositories, OpenAmiga.org for anything possibly sensitive and initial test materials,
and another site (undecided) for everyone to work from.

My other project "Polymorph" will only be partially documented.
It is a LOT more difficult to explain since it is based
on how some *simple* technical abstractions work together
to make one pretty dammed quick algorythm.

There is *nothing* new inside the way Polymorph works,
the only thing new is the way things are put together
using standard Amiga techniques.

@Mikey_C - Does a new one handling various Windows settings
as well as the Amiga Samba edition being made to work?

I have a recent samba config and just need to access things

I don't mind trying to document efforts to setup Win7 with AOS4.x and AmigaOS3.x c/o AMIthlon on QEMU

the PCI and PCIe-16 slottings is only a speed difference in the motherboard and card talking to each other...

when it comes to the chip on the card using video memory...
that doesn't really change (the PCI/PCI-E is system access)

the PCI slot will only dictate the maximum read/write
transfer to/from the graphics card and not much else that I know about.

Which sam model?

This card is currently above what is supported...

everything in the ATI range that is listed on wikipedia
with 4xxx numbering or earlier appears to have support
but the 5xxx numbering I have already bought and you are
currently looking at is still not yet properly supported.

If you buy it then you will be taking your own chances on
the issue of compatability is completely in your own hands.

I'm willing to accept the possible partial support if any,
along with needing to submit questions that may not be
answered due to NDA restrictions.

so you may want to find the highest 4xxx rating card with
an equal amount of memory.

anyway... take everything I have said and lookup the Radeon
Picasso96 driver compatability listing on hdrlab.org.nz

EDIT: fixed the URL

Well I will try to deal with making it as simple to use as possible,

But I already have in mind the most simplistic form of UI already...
but I will be dealing with "docky" material after I learn about programming in Amiga OS 4.x

I may yet need PortablE to deal with the Application end of things,
(I actually paid for Wouters 3.3 release of AmigaE)

But I know I will have to deal with mixing at least some assembler for one project in,
the catch being it will be multiple CPUs assembler...

Does anyone here really grok x86 and MIPS or ARM at the assembler level?
I can do the 680x0 and PPC without difficulties...

But I also have to wade into Java and Smalltalk opcodes as well...
hopefully I get to keep which processor is which sorted out!

I also have personal (real life) reasons to see this through
not just get it started but a complete Japanese locale
with both Language presentation (TrueType/OpenType fonts)
and language Entry (Complete IME Commodity & docky toolkit)

But I am also trying to make sure the framework allows for other languages as well, equally.
not just Japanese only, but a more generic IME.

That way Chinese and other languages can be more readily added as well.

I will be blogging and documenting everything as I work on this particular project.

Due to current changes in my life, I will also be actively working from in Japan directly and possibly also showing off the machine I am building as well.
I just need to finish paying for the core parts.

see os4coding.net for some of my blogged ramblings about this.

I've only just opened the door and begun things...
and I am stubborn enough to see things through

@Chris - Well I will definitely need to test and find out what works.

I'll get the IME framework into place before asking the devs about any changes only once they are proven to be needed.

Until that time I will try to do my best with what is already existing.

I'm already buying something which will be built into similar specs for ~400 Euro.

I wouldn't pay more than what I already am 2nd hand sam440 myself.
flex or otherwise.

I'll definitely be hunting for a sam460ex to pair off with it too and will need more sam440 machines later.

but having taken a year to find a decent deal on a sam440flex I'm in no rush to expand anything without being more properly sure of the hardware capabilities by dealing with one that I own.

I'm buying myself a sam440flex system 2nd hand first,
then I'll be adding to it with a sam460ex later on

Unless the X1000 price comes down a LOT I know I won't ever
actually afford one of those unless I get gifted one.

I'm not so worried about whether the board itself comes
with or without the OS (I'll buy the OS anyway if needed)

Heres to keeping at it with the voluntary test subjects and
seeing how twitchy things get :)

Hrmm... mad science is the thing I tells ya... mad science...
now what was up yes... oh... 240vAC to someones... OOHHH
THAT IS GONNA HURT I suspect...

@DAX: one of the reasons why I will need to find out what is needing to be patched and what will be
functional without patching, with a basic avoidance of patching anything unless absolutely needed.

I will need to find a list of beta-testers who have a range of software so that anything I introduce
does not force any major changes to anyone elses software.

The input changes will be on a highly limited basis and definitely open to suggestions

@trixie: I will be hooking into the standard text input routines and "buffering" the Input stream of characters...

Intuition will only see the "result string" I output from my own Input Handler (commodities filter level)
where commodities and other tools will remain unaffected

I will be dooing my utmost best to handle input properly
and as patchless as possible until I need otherwise.

@DAX certainly... right now I am only delayed in needing
to get hold of my developer machine

And I can certainly accept extra beta-testers.

Especially since the 4th edition of Cygnus Ed will be one
of my own primary test Applications.

@nbache

Is the "use the english name" recent for AOS4.x?

I have no experience coding for newer than Amiga OS 3.9
which was a lot of experimental materials

but if that is what is needed and documented for AOS4.x
then I'll put it together as "Japanese.language"
along with "chinese.language" for Chinese

@trixie

Yes, IME is Input Method Editor,

[edit]removed an extra chapter of book materials[/edit]

no point in wasting everyones time in repeating why I won't use any of the Emulators or cross-compilers and my negative experiences with them.