The Portable Freeware Collection Forums

Just a quick note: Even though i'm familiar with thinapp, i would have no idea what "exercise application" means (now i know - i usually do this during capture already). In my perspective, the "exercise application" in the thinapp is at step 3 and 4 as described in the thinapp m...

If you look at my mockup, one can conceivably click Project -> New, specify the EXE, then click Build -> Create portable package. There is no capture app files, and no analysis. You can do that under Analysis -> Exercise, but that part is optional. Yes, your idea is very clear to me. There are seve...

Andrew Lee, thanks for staying interested and discuss about this matter. Hope I have made myself clear, otherwise I may have to start resorting to diagrams. LOL, i already made it for you. Is it close to your idea in mind? Why I am proposing this is because it makes simple tasks simple. Say I want t...

Yup, i'm with you too on this one. The set of .ini selection could lead the beginner user at frustrated point which one should be use. Currently IMO, _Normal3.ini should be enough. So why not we eliminate that step. Just simply load the _Normal3.ini first in into GUI like JPE Config Modifier or a Wi...

Thanks for clarifying your GUI model. It can work that way too and reduce to few steps, especially for an app that is distribute in the archive (zip, 7z, rar). As such, there is no need to "re" anything here. Thank you. I think you're right and it make me think to revise my current process...

Guys, more shocking news.

Any comment

I would prefer that the "Build" step and the "Configure" step not be so distinct I'm not sure the level of distinct it could be but IMO, a separation is still required between "Build" step and "Configure" step. After the Build step finish, this is the point w...

I'm really impressed by your flowcharts, but I have very little understanding of the project you're posting about. Thanks. Yeah, probably you're right. My early post was too much of explaining things that were not related to GUI topic, which lead me to be in the frustrated situation to continue sha...

Thanks for reading, though it is quite disappointed to see nobody bother giving any comment. Below i made a proper process flow based on the mind map that i sketch before. Then i manage to explain the GUI model that could work with the process flow below. I have submitted the idea to redllar and cur...

When will do support Unicode? And will do? The JPE runtime is both ANSI and Unicode capable, as far as its internal processing goes. I'm not sure whether it will properly process Unicode config files. I know I put in code earlier to handle them, but I can't remember how far along I got with the tes...

Updated my post above to explain small part of my Mind Map. Comment please :) . There is one issue that can bring into further discussion. As we have two method of creating a Project, in your opinion which one is the more robust method? Both method have their own advantages and disadvantages What a ...

Not for now until JauntePE itself support Unicode.

When and will do for JauntePE?
I need to ask redllar about it..

My response to redllar in previous email is about the same as Andrew Lee. I do agree with Andrew Lee to have more comprehensive configuration ini document. There are still lot of settings that i never play with them yet. I had more detail response for the second email. The mind map below is the sum ...

Crownixx Thanks for this update. Great new features. are you gonna update this when redlar is updating JPE versions. I heard that he is back now and that is fantastic news. I love JPE portables. Yes, i'll update it to the latest JPE version but i still have some issues to fix. I try to post it soon...

A small favor by Redllar requesting for ideas/ feedback on new GUI for upcoming version 0.5.0. Originally, the request came from two separate emails. I quote the first email below, hopefully it could give you better explanation on redllar’s intention. … a new version (0.4.0) of the main JauntePE app...