12 replies to this topic

[pscEx]

I tried today and found that the good old .link does still (or again?) work.

Suggestion:

I split a new project 'nativeExCore' off 'nativeEx_barebone' and create a new download server for the core.
When splitting, in nativeEx_barebone the original scripts are replaced by .link files.

This should make it rather easy for LiveXP and NativePE, always to have the actual core.

What do you thik about that?

Peter

[Brito]

I agree with your idea and like the concept.

What if people only select the main server or thunn's server?

We'd be having lots of feedback mentioning that projects don't work (because the build scripts weren't downloaded).

Any idea to overcome this possible issue?

[pscEx]

What if people only select the main server or thunn's server?
We'd be having lots of feedback mentioning that projects don't work (because the build scripts weren't downloaded).

First idea: That is their problem!
Second Idea: That could be handled by a more intelligent download function in WinBuilder!
Third idea: Give me some time to think about this!
(maybe it can be combined with this)

Peter

[TheHive]

First idea: That is their problem!

lol! that cracked me up. I needed that.



I like the idea of having a core and a seperate project file. Very wise.

It can be handled by telling Winbuilder ini or something that the core needs to be downloaded for that project to work so when they select a project like NativeEx Barebones, LiveXP, or NativePE, or any others that may come and thus the core will be selected as part of the project.

That is why I had also suggested a long time ago to have the tools folder seperate from any of the other Projects because the way we have it now people have to know that they will need the tools folder download and/or NativePE or NativeEx Projects for them to work. So for example if one deselects the main server projects, the tools folder is gone. Let say a person just wants NativeEx project. They wont have the tools for it to work.

[Brito]

I've been thinking on adding more expandable features on the download center to optimize the current way how things are done.

One of the addons would be hability to read and merge folders from other update servers - this way we can avoid duplicate folders and people who don't download the appropriate tools from the "Tools" folder.

On this concept the whole build folder of liveXP (for example) could be directly linked to Peter's udpate server build folder and we would ensure that even if people deselect nativeEx they still get all latest files from the build folder. (this means of course that the external folder is stable and available online)

These links are done based on download level and not using the .link files placed on disk, this means that projects continue to have separate copies of the respective files, althought the same concept can also be discussed to be applied in the future where people would be allowed to add custom folders to their projects (on common folders like an API folder for example)


This would also allow for all projects appear under a single root node to which selected webservers are added - no more confusions and much more user friendly, I wasn't predicting the hability to create "junctions" on the update servers but this seems a logical behavior to allow sharing a common base of projects, the build and tools folder on this case and also solve the duplicate files issues.

A lot more of proposed work to test and debug but I think the results should be worth the effort.

[pscEx]

I realized the idea and delivered to nativeEx server.

The actual 'nativeEx_barebone' is still available as http://psc.boot-land...one_2007_JUN_19
(0nly by dedicated download, not as WEB server for WinBuilder download)

Download 'nativeEx_core' and 'nativeEx_barebone' from nativeEx server.
(If that is a fresh start, also download 'Tools' from nativeEx and if necessary from Main server!)

Try the new 'Link' constallation.

Copy the *.Link files into your actual LiveXP or NativePE project, delete the corresponding *.Script files and build your project!

Tell us the results here!

BTW: Because of version changes I'm waiting for a couple of complains (to be solved here)

Peter

[TheHive]

Tried it, It creates bootable PE.
The Admin tools and the Fonts icons problem is still alive on this build under the control panel.
Admin Tools, I dont know if they are suppose to be showing and the icons are missing for Admin Tools and Fonts folder.

You should Activate the display Script as part of the minimum. It auto start in a bigger window then what im using. So qemu pops up to too big of a size. The 800X600 default is better to have.

This was all a new download.

Do we need the download both the Core and the barebones to make it work. Barebones is now dependent on having the core also downloaded right?

[pscEx]

You should Activate the display Script as part of the minimum. It auto start in a bigger window then what im using. So qemu pops up to too big of a size. The 800X600 default is better to have.

Explorer script version 031 now defaults to 800 * 600, w/o any additional tweak script.

Do we need the download both the Core and the barebones to make it work. Barebones is now dependent on having the core also downloaded right?

Barebone is simply 'any' project using the Core.

Peter

[pscEx]

I did a test with LiveXP:

• Download fresh LiveXP, nativeEx_barebone and nativeEx_Core
• Setup a small running LiveXP project with some apps, but not too much drivers etc
• Build the project: Runs
• Copy all *.Link from nativeEx_barebone to the corresponding LiveXP folders.
• In the LiveXP folders deleted the corresponding *.Script
• Merged script.project:[Variables] section of nativeEx_barebone into LiveXP
  • Delete all but the api definitions in LiveXP
  • Copy complete nativeEx into LiveXP
  • Change %ProjectName% to LiveXP
• Replaced script.project:[Verify] section of LiveXP by that of nativeEx_barebone
• Checked and corrected the options of the linked scripts
• Build the project: Runs!

Peter

[TheHive]

[Brito]

.link files are not working correctly under the script editor - they will cause an error when being opened. This could be solved but the newer codings only had in mind a direct link and not a linked file to edit - this means a very extensive recoding change.

Also another issue: imagine the cases when people only download liveXP and click play - their project doesn't build?

We've been seeing reports of people who only mark a project for download and don't read the message on the right pane asking to include the tools folder, let alone know that they must also include a separated folder with scripts needed to build the project.

And we would also get back to the same issues about people confused why linked files are used in the first place.

Maybe it would be better to keep away from .link files for now and think/try other solutions - that can make things simpler and directly editable.

[smiley]

I think that the best solution is to make updates.ini for a project to point to a common server. So only the additional files will be in Nuno's server, and when a user want to download Nuno's project, except from the files that exist in this server, winbuilder will include in the list the files that exist in the common server. Of course, it needs further coding in winbuilder but can prevent many troubles

The result will be that the files of the core project will exist only in the common server, but in the user's computer they will be copied to each project

[Brito]

Sounds a good idea, I was also planning to add the ability to merge different webservers and this way allow to keep separate projects/folders together - imagine for example the help documentation available on a place and being called from the main server - this way whenever it's needed to update a small portion of the server it becomes much easier than reupload everything from scratch.

[updates\aFolder]
myfile.exe=....
Test=Folder
MyOtherFiles=http://myserver.boot-land.net

But your suggestion still leaves open the same problem - these files would still be duplicated and we'd need to also modify completely the script editor for example.