Page 1 of 1

HMG

Posted: Sun Aug 03, 2008 9:03 pm
by mbelgrano
where are hosted cvs of minigui ?
Wich is the situation of linux minigui?

my dream is having in harbour capability of Visual WebGui (VWG) http://www.visualwebgui.com/vProject

Re: HMG

Posted: Mon Aug 04, 2008 1:38 am
by Roberto Lopez
mbelgrano wrote:where are hosted cvs of minigui ?
Please, read this:

http://hmgforum.com/viewtopic.php?p=21& ... 828b7c#p21
mbelgrano wrote: Wich is the situation of linux minigui?
At this moment: A little expreminet. Perhaps I could continue in the future (in the case that I get enough time to do it).
mbelgrano wrote: my dream is having in harbour capability of Visual WebGui (VWG) http://www.visualwebgui.com/vProject
Perhaps, Linux be a step that we should skip and jump directly to web development.

As I've said in Harbour list, IMHO the best choice could be PHP + Javascript, but, porting Harbour to PHP could take a lot of years of hard work for a team of highly experienced progarmers.

Sadly, the fast way (current harbour in cgi) is not a real solution, since CGI is not always available (perhaps excepting intranets).

Regards,

Roberto.

Re: HMG

Posted: Mon Aug 04, 2008 2:47 am
by Roberto Lopez
mbelgrano wrote: my dream is having in harbour capability of Visual WebGui (VWG) http://www.visualwebgui.com/vProject
Another possibility is Harbour To Java, then compile Java with the Google Web Toolkit (GWT).

So, (according GWT docs):

"Use GWT's Java-to-JavaScript compiler to distill your application into a set of JavaScript and HTML files that you can serve with any web server."
<...>
Why Translate Java Code to JavaScript?

Java technologies offer a productive development plaform, and with GWT, they can instantly become the basis of your AJAX development platform as well. Here are some of the benefits of developing with GWT:

* You can use all of your favorite Java development tools (Eclipse, IntelliJ, JProfiler, JUnit) for AJAX development.
* Static type checking in the Java language boosts productivity while reducing errors.
* Common JavaScript errors (typos, type mismatches) are easily caught at compile time rather than by users at runtime.
* Code prompting/completion is widely available.
* Automated Java refactoring is pretty snazzy these days.
* Java-based OO designs are easier to communicate and understand, thus making your AJAX code base more comprehensible with less documentation."

Regards,

Roberto.