View Full Version : [RDJPv3] Final Update Suggestions
QuickScriptz
05-05-2008, 07:21 PM
Hello Everyone,
As some of you may [not] know, I am the creator of the Radio DJ Panel. We currently have a new version called "Radio DJ Panel v4" in the labs but we aren't sure how long it will be until it's release so we've decided to do one last final update to v3 in the meantime to fix those little things that would make the panel that much better.
We are looking for suggestions on fixes/edits to current features already in the panel but note that we ARE NOT asking for new feature requests. So, if you have any suggestions then please feel free to post them below and we will take them into consideration for the final update of v3.
Thanks.
Hypertext
05-05-2008, 08:29 PM
I am the creator
to
We currently have
Everyone is obsessed with the "Royal" 'we'.
QuickScriptz
05-05-2008, 09:10 PM
Everyone is obsessed with the "Royal" 'we'.
Well, "I" am the original creator but "we" (my design/coding team) are looking for suggestions for the final update.
Anyways, back on topic - any suggestions?
GoldenMerc
05-05-2008, 09:46 PM
Will this carry the update for the values script? or will i have to stay on v3?
if so i wish not to have any updates on the value script as mine is maxed out.
QuickScriptz
06-05-2008, 11:27 AM
It won't be an update to the actual rare values script itself - it will scrictly update the core panel.
EDIT: What exactly do you mean by "maxed out"?
GoldenMerc
06-05-2008, 03:40 PM
It has everything i want :]
QuickScriptz
08-05-2008, 09:47 PM
Okay, thanks :)
Klydo
08-05-2008, 10:33 PM
Actually Charley, think you'll find most people refer "we" to their website. As they see it as a group rather than a single identity, this does change for a personal blog however. I always refer to any site I work on or build as "we" even if it's just me who's making it. However if I wish to describe something I did then I'd use "I".
QuickScriptz
09-05-2008, 02:14 AM
What Klydo said is very true. "We" doesn't necessarily to more than one person but can represent an entity, a party, a company, or a group. It's exact meaning has become somewhat generic but for most companies/firms it is perfectly acceptable to use "we" on the website as it is talking about the company as a whole rather than the individual(s) who run/own it. So ya... anyways...
Any other feature suggestions?
Klydo
09-05-2008, 07:39 AM
Don't know if you have this already but an album art output which allows you to display album art depending on the artist onto the website. Which could be done using Last.FM's API.
QuickScriptz
09-05-2008, 11:25 AM
Hm.... interesting idea. I checked the Last.FM site though and got:
Are you a developer?
We're working on a shiny new developer site and API. Until then, check out our docs for using Audioscrobbler data or learn more about scrobbling and other bits. Have fun!
Anyways like I said above that's more of a whole new feature set than just an update but I will consider that for v4. Thanks for your suggestion :)
+Rep
tinydudekiller
28-05-2008, 04:22 PM
At the moment (in v3) if you want to edit a DJs details, it currently makes you submit a new password as well (or, if you leave the password field blank, leaves it blank). Had to edit everyone's details one afternoon and unwittingly managed to reset everyone's password. Oops.
So if you could change it so you can edit names/emails without modifying the password, would be ace.
Oh, and admins being able to book other DJs into the timetable without having to login as them would be nice too :)
Rzoned
08-06-2008, 08:22 AM
i think what this dj panel
Needs is
1. everyone get there own request line. ( so people can't go on and just Delete all the requests on them)
2. put all the frontend stuff in a file so we know what goes to the front end
3. Perm Show Request. so dj's can request perm shows
4. more secure log in. so its harder for people to hack
there is my two cents in case it matters
CoolHostUK-Dom
08-06-2008, 09:40 AM
1. everyone get there own request line. ( so people can't go on and just Delete all the requests on them)
2. put all the frontend stuff in a file so we know what goes to the front end
4. more secure log in. so its harder for people to hack
1. Ill expand on that - how about only the person djing at that time + admins can see request line
2. Most of it is
4. Oh, and you'v hacked it have you?
Rzoned
08-06-2008, 07:40 PM
yes me and my friend when we were testing dj panels to see which one to use i hacked it with out him telling me info in 5 min
Decode
08-06-2008, 08:35 PM
yes me and my friend when we were testing dj panels to see which one to use i hacked it with out him telling me info in 5 min
Yeah, i bet you did :rolleyes:
Independent
09-06-2008, 01:51 AM
I think on the installer their should be a choice of features to be installed, and the rare values script being a modification, because many non-habbo websites use this panel, and it sort of kills the professionalism seeing a rare value script somewhere in the panel.
+ Release the frontend files decoded, because we can't exactly do much with them.
GoldenMerc
09-06-2008, 10:22 PM
The rare values script is a plugin, It cost ££ to buy it
Independent
10-06-2008, 05:08 AM
The rare values script is a plugin, It cost ££ to buy it
ah, good :)
Independent
11-06-2008, 11:33 AM
yes me and my friend when we were testing dj panels to see which one to use i hacked it with out him telling me info in 5 min
Haha!
What did you enter?
insert * where USERNAME
Couldn't edit other post btw.
QuickScriptz
12-06-2008, 04:21 AM
Wow... I didn't realize this thread was still active! Anyways, here's the scoop:
- "Edit DJ" bug: already on our to-do list
- Permanent show requests: highly unlikely for v3
- Secure/harder to hack: v3 wasn't easy, improved in v4
- Only DJ with current slot can view requests: happening or something similar
- Installer: rare values is a paid addon and doesn't install by default
Our current to-do list...
-----------------------Legend----------------------
>! = High Priority
>+ = Normal Priority
>- = Low Priority
>? = Possibility/Unknown
>~ = New feature
----------------------RDJP v3----------------------
-Graceful errors
>! Homepage and update page
>> Server is unreachable, etc.
-Requests
>+ Convert special chars to HTML entities
-Editing DJ
>! Don't overwrite password if field is blank
-Creating DJ
>! Remove Rare Reporter rank
Also, on a side note, if anyone does manage to "hack" the RDJP v3 it would be highly appreciated if you contacted me and let me know so I can patch the flaw.
EDIT: As for the decoded files, well we'll see. Maybe once I release v4 then I'll let out the v3 source code? Or I'm not exactly sure how I'll do it just quite yet but if anyone is in dire need of any of the un-encrypted files then just let me know and we'll work something out :)
Independent
12-06-2008, 04:43 AM
Wow... I didn't realize this thread was still active! Anyways, here's the scoop:
- "Edit DJ" bug: already on our to-do list
- Permanent show requests: highly unlikely for v3
- Secure/harder to hack: v3 wasn't easy, improved in v4
- Only DJ with current slot can view requests: happening or something similar
- Installer: rare values is a paid addon and doesn't install by default
Our current to-do list...
Also, on a side note, if anyone does manage to "hack" the RDJP v3 it would be highly appreciated if you contacted me and let me know so I can patch the flaw.
EDIT: As for the decoded files, well we'll see. Maybe once I release v4 then I'll let out the v3 source code? Or I'm not exactly sure how I'll do it just quite yet but if anyone is in dire need of any of the un-encrypted files then just let me know and we'll work something out :)
I recommend that you change some varibles and functions for v4 if it's using the same code, then release both ;)
V3 source and v4 panel
QuickScriptz
14-06-2008, 02:18 AM
I recommend that you change some varibles and functions for v4 if it's using the same code, then release both ;)
V3 source and v4 panel
Don't worry, I am totally revamping almost all of the code for v4. When I originally coded v3 I didn't properly implement functions and whatnot so I have to redo the entire code structure to make it easier to manipulate and modify.
Only thing though is that I don't think that'll I'll be using classes/OOP to do it as I personally just prefer the normal old way versus messing around with classes. I'll definitely use functions and that sort of things but classes are still a possibility I guess...
Anyways :)
Invent
14-06-2008, 02:29 AM
Scriptz, what engine/script are you using to encode your script? As if you really don't want people seeing the source you need to get a better one as the current one can be decoded within a few minutes.
Independent
14-06-2008, 04:28 AM
Scriptz, what engine/script are you using to encode your script? As if you really don't want people seeing the source you need to get a better one as the current one can be decoded within a few minutes.
True, I remember someone decoding it because they believed it contained a virus..
I think it was chrisgocrazyH.
Want to hide these adverts? Register an account for free!
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.