Subject:*
<
Name/Email:*
<
Message Icon:*
<
Select*
<
Message:*
<



Click the Preview to see the content in action.
Options:*
<
Confirmation Code*
<
8 - 5 = ?  
Input the result from the expression
Maximum attempts you can try: 10
*
<
     

Re: Xoops PowerTools a Java Project
by xuser on 2006/7/11 16:57:22

an interesting idea, it looks like a powerful tool which will simplify the progress of upgrade and hack. but i dont think its a good idea that insert hack tags into the source code. can we borrow some concepts from version control system?
Re: Xoops PowerTools a Java Project
by davidl2 on 2006/7/11 13:06:59

I'd certainly be interested in seeing the finished work. I can see uses for it, and the auto-login hack, as you said, is an interesting example.
Re: Xoops PowerTools a Java Project
by panigrc on 2006/7/11 12:43:37

I respect your point of view. I also know german so I understood what you are talking about. You believe that having a util for everything is wrong. You want focus here is my focus:

I want to make XOOPS as easy as possible for everyone ! And yes this app will not be perfect but I wanna implement many features that are done manually by now.
Answer please to a simple question. How much time spend to apply a hack such as autologin ?
Ok you say a few its quite simple you have one hack only so you dont have to think about it.
Lets say you wanna update xoops, then some hacked files will be overwritten, so you loose your hack.
You should apply it again but with new files downloaded from the developer of the hack.
Then apply it, again a few more minute.
Now think if you have 3 hacks or a php developer who hacked XOOPS to death !!!!
When a patch is released the developer punches its head against the WALL.
But fortunately we have demokracy so you are free to use whatever you wish.
Re: Xoops PowerTools a Java Project
by ghettonet on 2006/7/11 5:08:47

Quote:
Why not focus on one thing and do it perfectly?


That's a very good point, but I know, at least for me, that I'm always doing 1000 things at once, and could use a helper app. I got tired of going to a bunch of different sites (all mine) to check up on them so I made a XOOPS site to put it all on one place.

I don't know if that's just lazy or inventive.
Re: Xoops PowerTools a Java Project
by birdseed on 2006/7/10 22:33:29

Hi

Quote:

* Putting a file hack it will say wich files are needed they are modified and it will say wich exists or not. Also with a simple click the source code will be modified automatic.
* The new files will be uploaded automatically in ftp and old will be renamed so they will exist as a backup.
* It will even have the possibility of deinstallation of hack even if the old files do not exist.
* It will remember wich files you have modified so after 6 months when you will want to upgrade XOOPS to know what to make.
* It might export and it creates files hack from files of code php so as to you create easily yours hack having only it modifies the code, and a click in the program.


Hacks are called hacks because they have an unstructured nature. Your hack declaration system makes sense if everybody uses it. I'm not convinced that this will be the case.
At my site, i disallowed ftp access and introduced cvs upload for source code and the XOOPS image manager for media upload.
All the features can be done by implementing a cvs. cvs is a well-known and stable (did i really say stable? ;) ) technology for source control.

Quote:

The precedents were the operations of application with regard to hacks. Now will exist also other functions wich will optimise with regard to as generally speaking xoops. These will be:
* Possibility of export in csv the names and email the users so as to they can be used from independent program as thunderbird, outlook etc.


..a typical client side application...
Quote:

* image Checking, will look at if exist all the pictures (links) that are reported in the database, if some does not exist it will be recorded.
* Link Checking, will take a table and a field that we will put in and it will check if all links that exist and aren't dead(here are required powerful regular expressions).


We did that for AMS. Can be easily done on the server

Quote:

* Cleaning/Optimizing the database.
* Backup of base of data in form that would not spoil the data. (If you tryed to make a backup with phpmyadmin and utf-8 you know what I mean.
* Reconstruction of table templates which faces problems after a lot of upgrades.
* Automatic reproduction of files of language so if you do not have all modules translated it won't be needed to make it manually.
* Export of text of files of language so with a copy paste of the text in certain translational tool, the text will be translated and later again with copy paste are created the certain files of language automatically (perhaps with some errors).
* Facility in the use of pictures, with few clicks change all icons that XOOPS and its modules use, that it is very difficult to make it manually. Of course it will upload the new pictures.
* Creation of themes of pictures ready to use that will become as I reported before. These will be the operations that will make my application. Also I should report that the application will have multilanguage support because I make it as XOOPS with language files.


In germany we say "eierlegende Wollmilchsau"... I`m missing a clear concept what the software should do. Why not focus on one thing and do it perfectly?

greetings
bsm

Who's Online

137 user(s) are online (95 user(s) are browsing Support Forums)


Members: 0


Guests: 137


more...

Donat-O-Meter

Stats
Goal: $15.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $15.00
Make donations with PayPal!

Latest GitHub Commits