|
just data-bind the class to an observable in your viewmodel and then update the observable when you want 2 change class.
|
#
?
Jun 5, 2014 02:06
|
|
|
|
| # ? May 12, 2024 17:53 |
|
|
Shaggar posted:just data-bind the class to an observable in your viewmodel and then update the observable when you want 2 change class. actually, if I want to change class I just go visit Bahamut.
|
|
#
?
Jun 5, 2014 02:40
|
|
|
FamDav posted:no i mean like lets say i do some some poo poo like just so we can have the full scope of how bad your situation is, why are you trying to do that in javascript instead of css or html?
|
|
#
?
Jun 5, 2014 02:46
|
|
|
Shaggar posted:just data-bind the class to an observable in your viewmodel and then update the observable when you want 2 change class. this is correct. also use angular.
|
|
#
?
Jun 5, 2014 02:48
|
|
|
Citizen Tayne posted:actually, if I want to change class I just go visit Bahamut.
|
|
#
?
Jun 5, 2014 02:48
|
|
|
HTML5 posted:this is correct. also use angular. angular looks stupid and overly complicated.
|
|
#
?
Jun 5, 2014 02:52
|
|
|
Shaggar posted:angular looks stupid and overly complicated. it is. if you have to write a javascript use knockout
|
|
#
?
Jun 5, 2014 03:02
|
|
|
I'd sooner starve tbqh
|
|
#
?
Jun 5, 2014 08:14
|
|
|
I just picked the smallest example of modifying a document.
|
|
#
?
Jun 5, 2014 13:51
|
|
|
lol i'm trying to fix the javascript of some long-gone shitbird and that is exactly the line i'm encountering. looks like this guy was just following the jquery tutorial too
|
|
#
?
Jun 5, 2014 15:26
|
|
|
he works for apple now
|
|
#
?
Jun 5, 2014 15:26
|
|
|
anyway, somebody teach me javascript, please.
|
|
#
?
Jun 5, 2014 15:27
|
|
|
is OSGI something I should know about if I'm doing java? Neither the wikipedia page or the official homepage offer a good explanation of what it actually is.
|
|
#
?
Jun 5, 2014 15:48
|
|
|
Werthog 95 posted:anyway, somebody teach me javascript, please. http://jquery.com/
|
|
#
?
Jun 5, 2014 15:48
|
|
|
more like dICK posted:is OSGI something I should know about if I'm doing java? Neither the wikipedia page or the official homepage offer a good explanation of what it actually is. osgi was an attempt to standardize a lot of the things left un-finished in j2se and/or botched in j2ee: classloader details, dependent components, application lifecycle like all attempts to standardize it is really complicated. i have worked on osgi applications and i can't really explain osgi to you, like 90% of the code ended up a single bundle
|
|
#
?
Jun 5, 2014 15:51
|
|
|
more like dICK posted:is OSGI something I should know about if I'm doing java? Neither the wikipedia page or the official homepage offer a good explanation of what it actually is. osgi is a generic plugin architecture where you can both import/export services.It lets you communicate across the plugin boundary through a service registry. it's been ~5 years since i had to write any osgi, i wrote an osgi wrapper for jython
|
|
#
?
Jun 5, 2014 16:08
|
|
|
tef posted:i wrote an osgi wrapper for jython he's seen j-beams glitter off the tannhauser gate things you wouldn't believe
|
|
#
?
Jun 5, 2014 16:11
|
|
|
ask me about eclipse internals did i ever tell you about using swt? it was bad enough that it was littered with pre 1.5 isms, so we had a ton of boilerplate around it to convert things to Arrays from Lists the widget set was 'cross platform', which meant everything worked differently across platforms. the vertical slider went from 0 to 100 on two platforms, and 100 to 0 on another tooltips couldn't be displayed on a secondary display if it was left of the primary monitor if you tried to have an updating tooltip, on one platform you could update the text, and it worked. on another platform, you had to use two tooltips and flick between them like some horrible throwback to double buffering
|
|
#
?
Jun 5, 2014 16:21
|
|
|
i tried to write a non-portable swt app, targeting only x11 (my entire userbase was linux), and failed. like, just failed. couldn't fix my own bugs, couldn't find anyone who could help. there's a good reason only two applications have ever used swt. the look and feel is way nicer than swing but that's not enough
|
|
#
?
Jun 5, 2014 16:24
|
|
|
have a look at this swt issue would you ?
|
|
#
?
Jun 5, 2014 16:26
|
|
|
more like dICK posted:is OSGI something I should know about if I'm doing java? Neither the wikipedia page or the official homepage offer a good explanation of what it actually is. you know how app containers basically don't work? osgi is an attempt to solve this by adding lots of complexity
|
|
#
?
Jun 5, 2014 16:55
|
|
|
OSGI is the one topic in the big lovely class i had this year that absolutely nobody understood, it was horrible
|
|
#
?
Jun 5, 2014 16:56
|
|
|
so i'm trying to fix this javascript and i've never javascripted before using the firefox debugger and it keeps breaking and offering no obvious reasoning as to why it broke. i have no breakpoints set so i assume it's an unhandled exception but i don't see any information about exceptions and i don't even know if javascript has exceptions help
|
|
#
?
Jun 5, 2014 16:57
|
|
|
Werthog 95 posted:so i'm trying to fix this javascript and i've never javascripted before Javascript is completely unrelated to Java, which owns. haha.
|
|
#
?
Jun 5, 2014 16:57
|
|
|
Werthog 95 posted:so i'm trying to fix this javascript and i've never javascripted before ctrl-z your code and keep executing till you find a point where it doesnt break, then figure out what line you added that broke it!!!
|
|
#
?
Jun 5, 2014 16:59
|
|
|
Kevin Mitnick P.E. posted:you know how app containers basically don't work? osgi is an attempt to solve this by adding lots of complexity the complexity was aleays there but often hidden. debugging classloader issues is hell. porting apps between j2ee implementations is sometimes effortless and sometimes bottomless suffering. osgi gets really specific about classloader behavior and the order in which things get instantiated, because j2ee didn't
|
|
#
?
Jun 5, 2014 17:02
|
|
|
i mean "break" as in the debugger broke u dork. why is the debugger breaking.
|
|
#
?
Jun 5, 2014 17:02
|
|
|
i don't really understand osgi but i understand at least one of their design goals
|
|
#
?
Jun 5, 2014 17:02
|
|
|
Werthog 95 posted:so i'm trying to fix this javascript and i've never javascripted before what is breaking in this sense? it stops running at a certain point? is there an ajax call or something that is asynchronous that fails? the non-debugger browser console (not the web console) does not show an error either? Share Bear fucked around with this message at 17:08 on Jun 5, 2014 |
|
#
?
Jun 5, 2014 17:03
|
|
|
Share Bear posted:what is breaking in this sense? it stops running at a certain point? is there an ajax call or something that is asynchronous that fails? the debugger breaks in a callback from a jquery function but the particular line it breaks on seems fine. no errors in the browser console anyway oh and removing a comment fixed it 
|
|
#
?
Jun 5, 2014 17:19
|
|
|
its hard to track down stuff when you have 1000 lines of code wrapped up in one function, then when something fails it just reports the problem being at like line 26 where the outside function starts, helpful!Werthog 95 posted:oh and removing a comment fixed it ive had this happen with C code before lol
|
|
#
?
Jun 5, 2014 17:21
|
|
|
the IE debugger doesn't do it, lol. shaggar was right.
|
|
#
?
Jun 5, 2014 17:27
|
|
|
Notorious b.s.d. posted:the complexity was aleays there but often hidden. right i mean making app containers work properly is super complex. osgi moves that complexity into the spec. hooray? i suppose someone has a use for it but i've never met them
|
|
#
?
Jun 5, 2014 17:33
|
|
|
the real answer to classloader/container hell: embed jetty in your app, run every component in its own jvm and its own unix service. i used to poke fun at devs who did this until i tried it for myself in a hobby app. never, ever going back.
|
|
#
?
Jun 5, 2014 17:36
|
|
|
Notorious b.s.d. posted:the real answer to classloader/container hell: embed jetty in your app, run every component in its own jvm and its own unix service. I just started doing this as well. I got really sick of having to janitor Tomcat + WARs, so now every app is its own JAR that starts up jetty, and starts listening for HTTP connections from the load balancer. Surprisingly little code required to move from WAR + Tomcat to an embedded servlet container. My opinion of Java really changed once I started doing this. edit: I like a lot of Java now. I'm worried that makes me a bad or dumb person. more like dICK fucked around with this message at 18:06 on Jun 5, 2014 |
|
#
?
Jun 5, 2014 17:52
|
|
|
Notorious b.s.d. posted:the real answer to classloader/container hell: embed jetty in your app, run every component in its own jvm and its own unix service. hold up, you mean people deploy java into shared environments like some horror from 90's web development?
|
|
#
?
Jun 5, 2014 18:23
|
|
|
tef posted:ask me about eclipse internals swt is awful and is based firmly in 1.4. the eclipse org refuses to update it which is so aggravating.
|
|
#
?
Jun 5, 2014 18:25
|
|
|
tef posted:hold up, you mean people deploy java into shared environments like some horror from 90's web development? an application often has more than one component, and servlet containers make it easy to combine them in a single jvm e.g. api.war mounts at server:8080/api web.war mounts at server:8080/web since they're parts of the same application it often makes sense to keep them together in one host unfortunately when you get a lot of components, or they depend on each other for rest/soap/xmlrpc/rmi web services, poo poo starts to get hairy. what if tomcat deploys a war in the wrong order, and one comes up before the other? also the LB effort starts to get stupid, since you effectively have independent services listening on a single ip:port combination in embedded jetty or w/ on-the-fly provisioning every servlet gets its own jvm and its own ip endpoint
|
|
#
?
Jun 5, 2014 18:26
|
|
|
people who have classloader problems in tomcat are people who hosed up their tomcat install and/or war layout. if you are putting jars anywhere under {tomcat}/common you should be murdered
|
|
#
?
Jun 5, 2014 18:29
|
|
|
|
| # ? May 12, 2024 17:53 |
|
|
Shaggar posted:people who have classloader problems in tomcat are people who hosed up their tomcat install and/or war layout. if you are putting jars anywhere under {tomcat}/common you should be murdered it's j2ee app servers with tons of custom classloaders that tend to gently caress things up, less tomcat. it still happens with tomcat but less often see also: fucksticks who mess with oneJar and its ilk
|
|
#
?
Jun 5, 2014 18:32
|
|